docs(changelog): cut 2.0.0 — fold Unreleased + post-cutover work#59
Merged
Conversation
Scriptor 2.0 was never tagged. Everything since the rewrite sat under two unfinished buckets in the CHANGELOG: "## Unreleased" (the public/-webroot refactor) plus "## 2.0.0 — Ground-up rewrite" (the core rewrite itself, no date). On top of those, several shipped PRs weren't captured at all: domain rebrand, demo-seed-from-scriptor.cms, docker volume split, two-image stack, X-Forwarded-Proto trust, FTS re-create after seed restore, iManager 2.0.1 bump, security headers hardening, cookie flags. Folded into one dated "2.0.0 (2026-05-16)" section, organised by keepachangelog subsections (Added / Fixed / Changed BREAKING / Changed / Security / Removed / Migration / Performance). The intent is a single release entry that tells the full 2.0 story — rewrite + reorganisation + deploy hardening — instead of three half-finished ones. Follow-up: tag v2.0.0 on master once this lands.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scriptor 2.0 was never tagged. Everything since the rewrite sat under two unfinished buckets in the CHANGELOG: "## Unreleased" (the public/-webroot refactor) plus "## 2.0.0 — Ground-up rewrite" (the core rewrite itself, no date). On top of those, several shipped PRs weren't captured at all: domain rebrand, demo-seed-from-scriptor.cms, docker volume split, two-image stack, X-Forwarded-Proto trust, FTS re-create after seed restore, iManager 2.0.1 bump, security headers hardening, cookie flags.
Folded into one dated "2.0.0 (2026-05-16)" section, organised by keepachangelog subsections (Added / Fixed / Changed BREAKING / Changed / Security / Removed / Migration / Performance). The intent is a single release entry that tells the full 2.0 story — rewrite + reorganisation + deploy hardening — instead of three half-finished ones.
Follow-up: tag v2.0.0 on master once this lands.